Skip to content

fix: handle Linux secret-service fallback for API keys#1905

Open
tsubasakong wants to merge 1 commit intokoala73:mainfrom
tsubasakong:lucas/issue-802-linux-vault
Open

fix: handle Linux secret-service fallback for API keys#1905
tsubasakong wants to merge 1 commit intokoala73:mainfrom
tsubasakong:lucas/issue-802-linux-vault

Conversation

@tsubasakong
Copy link
Contributor

Summary

  • detect Linux Secret Service / DBus activation failures when saving the consolidated desktop secrets vault
  • fall back to the Linux kernel keyring (keyutils) so API keys can still be saved in headless / Wayland sessions without an activatable Secret Service backend
  • load previously saved fallback secrets on startup and clear the fallback entry once the normal keyring path succeeds again

Testing

  • cargo check
  • cargo test secret_storage_tests --bin world-monitor

Fixes #802

@vercel
Copy link

vercel bot commented Mar 20, 2026

@tsubasakong is attempting to deploy a commit to the Elie Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions bot added the trust:caution Brin: contributor trust score caution label Mar 20, 2026
@koala73 koala73 added High Value Meaningful contribution to the project Ready to Merge PR is mergeable, passes checks, and adds value labels Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

High Value Meaningful contribution to the project Ready to Merge PR is mergeable, passes checks, and adds value trust:caution Brin: contributor trust score caution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unable to add any api keys on linux version

2 participants